feat: support multiple GitHub organizations - #379

Description

Discover public repositories from the shared LizardByte/.github/organizations.json registry and show metrics across organizations, with an organization filter and owner-qualified repository/PR links. Same-name repositories in different organizations remain distinct. Chart labels use short repository names, with the owner on a second line only for duplicates; hover details retain the full identity.

Keep existing cache keys by GitHub repository ID across transfers and renames. Restore the published history, banners, badges, and identity catalog before collection; merge Codecov history by timestamp and retain cached data when an organization or code-scanning API is unavailable. Repositories without Codecov uploads are skipped until active, so an org with no coverage data does not produce a false collection warning. Existing badge/banner URLs and original PR-report routes continue to work. New repositories use owner-qualified storage keys, and the raw repository catalog exposes their asset paths.

Azure collection remains opt-in, with cache-only PR builds.

Screenshot

Issues Fixed or Closed

Roadmap Issues

Testing

• Python: 158 tests passed with 100% coverage (pytest with an explicit writable temporary directory).
• JavaScript: 35 tests passed with 100% line and branch coverage (jest --runInBand --coverage).
• flake8 src tests, npm run lint, and git diff --check passed.
• Added transfer/rename, duplicate-name, registry/API outage, public-only discovery, Codecov pagination/history, organization-filter, PR-link, readable chart/legend labels, full hover identities, inactive Codecov projects becoming active after upload, and original report-route tests.
• Code-scanning cache-loss regressions failed for HTTP 403 and 404 before the retention fix and pass afterward.
• Read-only rehearsal using the published cache and live discovery succeeded for all five organizations and 84 public repositories. Simulated the seven planned transfers; all 10 sampled history/badge/banner file checksums were unchanged, and both original and owner-qualified Sunshine report routes were generated.

Local validation is complete; hosted checks are running for the latest commit. Browser screenshot preview was unavailable in this session. The local rehearsal does not transfer repositories or publish a site.

Type of Change

• feat: New feature (non-breaking change which adds functionality)
• fix: Bug fix (non-breaking change which fixes an issue)
• docs: Documentation only changes
• style: Changes that do not affect the meaning of the code (white-space, formatting, missing semicolons, etc.)
• refactor: Code change that neither fixes a bug nor adds a feature
• perf: Code change that improves performance
• test: Adding missing tests or correcting existing tests
• build: Changes that affect the build system or external dependencies
• ci: Changes to CI configuration files and scripts
• chore: Other changes that don't modify src or test files
• revert: Reverts a previous commit
• BREAKING CHANGE: Introduces a breaking change (can be combined with any type above)

Checklist

• Code follows the style guidelines of this project
• Code has been self-reviewed
• Code has been commented, particularly in hard-to-understand areas
• Code docstring/documentation-blocks for new or existing methods/components have been added or updated
• Tests have been added or updated for new or modified functionality, including regression tests for bug fixes

AI Usage

See our AI usage policy.

• AI tools were used while preparing this PR